Intelligently enabled menu choices based on online presence state in address book

ABSTRACT

A computer implemented method for intelligently enabling menu choices includes rendering, on a client system, an address book user interface comprising information related to one or more contacts, selecting a contact from the address book user interface, determining an online presence state for the selected contact, enabling one or more menu options based upon the determined online presence state, with the menu options enabled for a first online presence state differing from the menu options enabled for a second online presence state, and presenting the enabled menu options to a user in a user interface.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 13/396,132 filed on Feb. 14, 2012, which is a continuation of U.S. application Ser. No. 10/633,636 filed on Aug. 5, 2003 and now issued as U.S. Pat. No. 8,132,110, which is a continuation in part of U.S. application Ser. No. 09/848,231 filed on May 4, 2001 and now issued as U.S. Pat. No. 8,122,363, which claims the benefit of U.S. Provisional Application Nos. 60/229,331 filed on Sep. 1, 2000 and 60/201,738 filed on May 4, 2000. Each of the aforementioned applications and patents are hereby incorporated by reference in their entirety.

TECHNICAL FIELD

This description relates to intelligently enabling menu choices and more particularly to intelligently enabling menu choices based upon online presence state information.

BACKGROUND

Online service providers facilitate access to information and services by providing interactive user interfaces (UIs) that help users (e.g., subscribers) navigate to desired resources. For example, in the case of a system for communicating using instant messages (IMs), a UI allows a user to invoke actions, such as establishing a communications link, through the selection of screen objects such as icons, windows, and drop-down menus. The design of a UI has a significant impact on a user's online experience. In particular, the icons, the windows, and the menus of a UI may be arranged to enable a user to locate information and services quickly and easily.

SUMMARY

In one general aspect, a computer implemented method for intelligently enabling menu choices includes rendering, on a client system, an address book user interface comprising information related to one or more contacts, selecting a contact from the address book user interface, determining an online presence state for the selected contact, enabling one or more menu options based upon the determined online presence state, with the menu options enabled for a first online presence state differing from the menu options enabled for a second online presence state, and presenting the enabled menu options to a user in a user interface.

Implementations may include one or more of the following features. For example, the menu options may correspond to one or more available communications channels, and the available communications channels may include e-mail, chat, and/or instant messaging. Determining the online presence state may include receiving the online presence state from a host system, and the online presence state may include an online state, a mobile device usage state, an idle state, an away state, an offline state, and/or a not IM capable state.

A menu may be invoked for the selected contact. In one implementation, enabling the menu options may include enabling the menu options by retrieving a list of one or more pre-stored menu options associated with the determined online presence state. The menu options may be automatically determined by the client system or host system. In another implementation, the menu options may be enabled on-the-fly (e.g., dynamically enabled), and may be enabled automatically by the client system or by the host system. Enabling the menu options may include adding a control, making a control unavailable, removing a control, and changing a control.

Implementations of presenting the enabled menu options include presenting the determined online presence state for the contact, presenting the menu options in the address book user interface, and presenting only the enabled menu options in a user interface.

In another general aspect, a user interface enables perception of enabled menu choices and includes an address book application user interface that enables perception of information for one or more contacts for an address book user, a mechanism that determines an online presence state for one or more contacts, a mechanism that enables one or more menu options for a contact based upon the online presence state of the contact, with menu options enabled for a first online presence state differing from menu options enabled for a second online presence state, and a mechanism that presents the enabled menu options to the address book user.

Implementations may include one or more of the following. For example, the menu options may correspond to one or more available communications channels and the available communications channels may include e-mail, chat, and instant messaging. The mechanism that determines the online presence state includes a mechanism that receives the online presence state from a host system. The determined online presence state includes an online state, a mobile device usage state, an idle state, an away state, an offline state, and a not IM capable state.

In one implementation, the mechanism that enables the menu options may include a mechanism that enables the menu options by retrieving a list of one or more pre-stored menu options for the determined online presence state, and the menu options may be automatically enabled by the client system or the host system. In another implementation, the mechanism that enables the menu options includes a mechanism that enables the menu options on-the-fly. The mechanism that enables the menu options may include a mechanism that adds a control, a mechanism that makes a control unavailable, a mechanism that removes a control, and/or a mechanism that changes a control.

The mechanism that presents the enabled menu options may include a mechanism that presents the determined online presence state for the contact or a mechanism that presents only the enabled menu options. The mechanism that presents the enabled menu options may be, for example, the address book application user interface.

Aspects of the intelligently enabled menu choices may be implemented by an apparatus and/or by a computer program stored on a computer readable medium. The computer readable medium may comprise a disc, a client device, a host device, and/or a propagated signal. In addition, aspects of the intelligently enabled menu choices may be implemented in a client/host context or in a standalone or offline client device. The intelligently enabled menu choices may be rendered in a client/host context and may be accessed or updated through a remote device in a client/host environment. The intelligently enabled menu choices also may be rendered by the standalone/offline device and may be accessed or updated through a remote device in a non-client/host environment such as, for example, a LAN server serving an end user or a mainframe serving a terminal device.

Other features will be apparent from the following description, including the drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIGS. 1-3 are block diagrams of an exemplary communications system.

FIGS. 4A, 4B, & 4C are flow charts of exemplary processes that may be implemented by systems such as those of FIGS. 1-3.

FIGS. 5-12 are illustrations of different graphical user interfaces that may be implemented by systems such as those of FIGS. 1-3 when executing a process such as those of FIGS. 4A, 4B, & 4C.

For brevity, several elements in the figures described below are represented as monolithic entities. However, as would be understood by one skilled in the art, these elements each may include numerous interconnected computers and components designed to perform a set of specified operations and/or may be dedicated to a particular geographic region.

DETAILED DESCRIPTION

The described systems and techniques allow intelligently enabled menu choices to be made available to a user of an address book based upon the online presence state (online state) of a contact in the user's address book. An address book enables a user to communicate with any of the listed contacts using any of the available communications channels (e.g., communications schemes), such as, for example, e-mail, IM, telephone, and U.S. Mail. The user is not limited to viewing and contacting a subset of contacts sharing a common communication channel. Also, the contacts in the address book need not share any common communication channel. The available communications channels for communicating with a contact may differ depending on, for example, the instant messaging online presence state of the contact. Thus, using the address book, communications are enabled through available communication channels to any contact with whom the user is able to communicate.

Menu choices may be determined and presented to a user based on the online presence state of the contact. The determined menu choices may include choices for automatically presenting and configuring appropriate communications channels which may be used for communicating with a selected contact based upon the online presence of the selected contact. For example, certain menu choices may only be appropriate when a contact is online, and such choices will only be made available to the user when the contact is online. The choices made available to the user may depend on other available online states, such as an indication that the contact is using a mobile device, has been inactive for a certain period of time, has set an indication of being away or unavailable, has enabled or disabled the user's ability to detect the contact's presence, is offline, or does not have instant messaging capability. The online states available to the user typically depend upon the communications system being used.

Although online presence is discussed below primarily with respect to IM applications, other implementations are contemplated for providing similar online presence functionality in platforms and online applications such as chat applications or e-mail applications. The provision of such status in an address book or other non-communications application enables a user to focus on available actions with respect to the contacts themselves without needing to pay attention to any particular communications channel available to communicate with a particular contact.

For illustrative purposes, FIGS. 1 and 2 show an example of a communications system for implementing techniques for transferring electronic data. Referring to FIG. 1, a communications system 100 is capable of delivering and exchanging data between a client system 105 and a host system 110 through a communications link 115. The client system 105 typically includes one or more client devices 120 and/or client controllers 125, and the host system 110 typically includes one or more host devices 135 and/or host controllers 140. For example, the client system 105 or the host system 110 may include one or more general-purpose computers (e.g., personal computers), one or more special-purpose computers (e.g., devices specifically programmed to communicate with each other and/or the client system 105 or the host system 110), or a combination of one or more general-purpose computers and one or more special-purpose computers. The client system 105 and the host system 110 may be arranged to operate within or in concert with one or more other systems, such as, for example, one or more LANs (“Local Area Networks”) and/or one or more WANs (“Wide Area Networks”).

The client device 120 and the host device 135 are generally capable of executing instructions under the command of, respectively, a client controller 125 and a host controller 140. The client device 120 and the host device 135 are connected to, respectively, the client controller 125 and the host controller 140 by, respectively, wired or wireless data pathways 130 and 145, which are capable of delivering data.

The client device 120, the client controller 125, the host device 135, and the host controller 140 typically each include one or more hardware components and/or software components. An example of a client device 120 or a host device 135 is a general-purpose computer (e.g., a personal computer) or software on such a computer capable of responding to and executing instructions in a defined manner. Other examples include a special-purpose computer, a workstation, a server, a device, a component, other physical or virtual equipment, or some combination of these capable of responding to and executing instructions. The client device 120 and the host device 135 may include devices that are capable of establishing peer-to-peer communications.

An example of client controller 125 or host controller 140 is a software application loaded on the client device 120 or the host device 135 for commanding and directing communications enabled by the client device 120 or the host device 135. Other examples include a program, a piece of code, an instruction, a device, a computer, a computer system, or a combination of these for independently or collectively instructing the client device 120 or the host device 135 to interact and operate as described. The client controller 125 and the host controller 140 may be embodied permanently or temporarily in any type of machine, component, physical or virtual equipment, storage medium, or propagated signal capable of providing instructions to the client device 120 and the host device 135.

The communications link 115 typically includes a delivery network 160 that provides direct or indirect communication between the client system 105 and the host system 110, irrespective of physical separation. Examples of a delivery network 160 include the Internet, the World Wide Web, WANs, LANs, analog or digital wired and wireless telephone networks (e.g., Public Switched Telephone Network (PSTN), Integrated Services Digital Network (ISDN), and Digital Subscriber Line (xDSL)), radio, television, cable, or satellite systems, and other delivery mechanisms for carrying data. The communications link 115 may include communication pathways 150 and 155 that enable communications through the one or more delivery networks 160 described above. Each of the communication pathways 150 and 155 may include, for example, a wired, wireless, cable or satellite communication pathway.

FIG. 2 illustrates a communications system 200 including a client system 105 communicating with a host system 110 through a communications link 115.

The client system 105 includes a client device 120 that typically includes a general-purpose computer 270 having an internal or external memory 272 for storing data and programs such as an operating system 274 (e.g., DOS, Windows™, Windows 95™, Windows 98™, Windows 2000™, Windows Me™, Windows XP™, Windows NT™, OS/2, or Linux) and one or more application programs. Examples of application to programs include authoring applications 276 (e.g., word processing programs, database programs, spreadsheet programs, or graphics programs) capable of generating documents or other electronic content; client applications 278 (e.g., America Online (AOL) client, CompuServe client, AOL Instant Messenger (AIM) client, interactive television (ITV) client, Internet Service Provider (ISP) client, or instant messaging (IM) client) capable of communicating with other computer users, accessing various computer resources, and viewing, creating, or otherwise manipulating electronic content; and browser applications 280 (e.g., Netscape's Navigator or Microsoft's Internet Explorer) capable of rendering standard Internet content and other content formatted according to standard protocols such as the Hypertext Transfer Protocol (HTTP).

One or more of the application programs may be installed on the internal or external storage 272 of the general-purpose computer 270. Alternatively, in another implementation, the client controller 125 may access application programs externally stored in and/or performed by one or more device(s) external to the general-purpose computer 270.

The general-purpose computer 270 also includes a central processing unit 282 (CPU) for executing instructions in response to commands from the client controller 125, and a communication device 284 for sending and receiving data. One example of the communication device 284 is a modem. Other examples include a transceiver, a set-top box, a communication card, a satellite dish, an antenna, a network adapter, or some other mechanism capable of transmitting and receiving data over the communications link 115 through a wired or wireless data pathway 150. The general-purpose computer 270 optionally includes a television (“TV”) tuner 286 for receiving television programming in the form of broadcast, satellite, and/or cable TV signals. The TV tuner 286 permits the client device 120 to selectively and/or simultaneously display network content received by communications device 284 and TV programming content received by the TV tuner 286.

The general-purpose computer 270 may include an input/output interface 288 that enables wired or wireless connection to various peripheral devices 290. Examples of peripheral devices 290 include, but are not limited to, a mouse 291, a mobile phone 292, a personal digital assistant (PDA) 293, an MP3 player (not shown), a keyboard 294, a display monitor 295 with or without a touch screen input, a TV remote control 296 for receiving information from and rendering information to users, and an audiovisual input device 298.

Although FIG. 2 illustrates devices such as a mobile telephone 292, a PDA 293, and a TV remote control 296 as being peripheral with respect to the general-purpose computer 270, in another implementation, such devices may themselves include the functionality of the general-purpose computer 270 and operate as the client device 120. For example, the mobile phone 292 or the PDA 293 may include computing and networking capabilities and function as a client device 120 by accessing the delivery network 160 and communicating with the host system 110. Furthermore, the client system 105 may include one, some or all of the components and devices described above.

FIG. 3 illustrates a communications system 300 including a client system 105 communicating with a selected contact system 305 and an IM host system 310 through a communication link 115. The communications system 300 enables a user to communicate with a selected contact such as, for example, a selected contact listed in the user's address book. Such a communications system may be used by users of IM service providers, such as, for example, AIM, ICQ, Yahoo Messenger, and Microsoft Messenger. Typically, IM communications involve an instantaneous or nearly instantaneous communication between two users, where each user is able to transmit, receive and display communicated information. Additionally, IM communications generally involve the display and perception of online presence state information regarding other selected users (“buddies”). IM communications may be machine-to-machine communications that occur without intervention by or communication through an instant messaging server after a communication session is established or authentication is performed.

In one implementation, the IM host system 310 may have characteristics similar to those described above with respect to the host system 110, the selected contact system 305 may have characteristics similar to those described above with respect to the client system 105, and the client system 105 and the selected contact system 305 may include communication software to enable users of the client systems to access the IM host system 310.

The IM host system 310 may support IM services irrespective of an IM user's network or Internet access. Thus, the IM host system 310 may allow users to send and receive IMs, regardless of whether they have access to any particular ISP. The IM host system 310 also may support associated services, such as administrative matters, advertising, directory services, chat, and interest groups related to the IM. The IM host system 310 has an architecture that enables the devices (e.g., servers) within the IM host system 310 to communicate with each other. To transfer data, the IM host system 310 employs one or more standard or exclusive IM protocols.

To access the IM host system 310 to begin an IM session in the implementation of FIG. 3, the client system 105 establishes a connection to the IM host system 310. Once a connection to the IM host system 310 has been established, the client system 105 may directly or indirectly transmit data to and access content from the IM host system 310.

By accessing the IM host system, an IM user can use the IM client application to view whether particular users (“buddies”) are online, exchange IMs with particular buddies, participate in group chat rooms, trade files such as pictures, invitations or documents, find other buddies with similar interests, get customized information such as news and stock quotes, and search the Web. The selected contact system 305 may be similarly manipulated to establish a contemporaneous connection with IM host system 310.

Once connectivity is established, an IM user who is using client system 105 may view whether a selected contact using selected contact system 305 is online, and typically may view whether the selected contact is able to receive IMs. If the selected contact is online, the IM user may exchange IMs with the selected contact.

In one implementation, the IMs sent between client system 105 and selected contact system 305 are routed through IM host system 310. In another implementation, the IMs sent between client system 105 and selected contact system 305 are routed through a third party server (not shown), and, in some cases, are also routed through IM host system 310. In yet another implementation, the IMs are sent directly between client system 105 and selected contact system 305.

Referring to FIGS. 4A, 4B, and 4C, the client system 105 and the host system 110 interact according to exemplary procedures 400A, 400B, and 400C to intelligently enable menu choices for a user of an address book based upon the online presence state of a contact.

Procedures 400A, 400B, and 400C may be implemented by any type of hardware, software, device, computer, computer system, equipment, component, program, application, code, storage medium, or propagated signal. Although not shown in FIGS. 4A, 4B, and 4C, the client system 105 and the host system 110 may be directly or indirectly interconnected through known or described delivery networks, examples of which are described with respect to network 160.

The procedures 400A, 400B, and 400C may be implemented in a client/host context, or a standalone or offline client context. For example, while some functions of procedures 400A, 400B, and 400C may be performed entirely by the client system 105, other functions may be performed by host system 110 or by the collective operation of the client system 105 and the host system 110. The host system 110 is a computer remote to the instant messaging operator systems, and may be, for example, an IM host system 310. In procedures 400A, 400B, and 400C, the intelligently enabled menu may be respectively selected and rendered by the standalone/offline device, and the menu may be accessed or updated through a remote device in a non-client/host environment such as, for example, a LAN server serving an end user or a mainframe serving a terminal device. Thus, the procedures 400A, 400B, and 400C described below may be implemented for any OSP, ISP, browser and/or other software program having a graphical user interface, such as programs for instant messaging, chat, electronic mail and stand-alone browsers.

Referring to FIG. 4A and procedure 400A, the user loads or invokes an address book user interface (UI) (step 405). FIG. 5 describes an exemplary address book UI available to the user. The address book contains one or more contacts, along with information regarding the contact, such as name, address, telephone, e-mail address, and instant messaging screen name. Loading or invoking the address book may include populating the address book with contacts and information regarding the contacts, and also may include updating information about contacts in the address book.

The client system 105 logs in or otherwise accesses the host system 110 (step 410). For instance, client system 105 may connect to the host system 110 across a network (e.g., network 160) by supplying verifiable credentials to a server (e.g., a login server) at the host system 110. More specifically, a browser may be used to access a web-available interface, an IM client may be used to access a selectable interface, or an IM client that has an interface to a host may be used, among other options.

Next, the presence state of one or more contacts in the user's address book is detected by the host system 110 (step 415). In order for the host system to obtain the list of one or more contacts for whom online presence information is desired, the host may, for example, directly consult the user's address book if the address book is maintained at the host system 110. Alternatively, the host system 110 may store a list of one or more contacts at the host system 110 or other data store remote to the host, or the client system 105 may pass a list of one or more contacts to the host system 110. The list of one or more contacts may include all of the contacts in the user's address book, less than all of the contacts in the user's address book, a selected contact or group of contacts specifically designated by the user, or contacts visible in the address book UI displayed to the user.

After detecting the presence state of the one or more contacts, the host system 110 may send or otherwise make accessible to the client system 105 the presence state information for each of the one or more contacts (step 420). Sending the presence state information may include sending a code or information corresponding to the online presence state of the contact. For example, the host system 110 may send a code corresponding to a presence state of online, using a mobile device, idle, away, offline, or not IM capable (e.g., does not have an IM screen name or does not participate in an instant messaging service). Other presences states may be included as appropriate.

The online presence state of the one or more contacts is then received or accessed by the client system 105 (step 425). The user is enable to perceive the online presence state of the one or more contacts, and the online presence state may be displayed to the user. FIG. 6 illustrates an exemplary interface available to the user, which will be described below, and which may be used to display online presence information for an address book contact.

Next, a contact is selected by the user (step 430). FIG. 6, described below, illustrates an exemplary interface available to the user that may be used to select a contact. More than one contact may be selected.

A menu then is invoked for the selected contact (step 435). The menu may be invoked through user manipulation of a UI, such as the address book UI. After invoking the menu, a determination is made as to whether the selected contact is IM capable (step 437). If the selected participant is not IM capable, then a set of menu options are determined for the selected non-IM capable contact (step 465) and the menu is rendered with the determined options (step 470). Determining the menu options may include configuring options for alternative communications channels based upon the online presence state. For example, when the selected contact is not IM capable, the communications channels may include e-mail but not IM. FIG. 12 illustrates an exemplary interface available to a user when the selected contact is not IM capable.

Next, a determination is made as to whether the selected contact is online (step 440). Depending upon the online presence state, different actions may be taken. Although described in terms of online versus offline menus in this example, other implementations are possible. For example, different actions could be taken based upon other online states, such as whether the contact is using a mobile device, has been inactive for a certain period of time, has set an indication of being away or unavailable, or has enabled or disabled the user's ability to detect the contact's presence.

If the selected contact is online, the online menu options are determined for the selected contact (step 445) and the menu is rendered with the online options (step 450). The online menu options are options which are desired to be presented to the user when the desired contact is online or otherwise available. Determining the online menu options may include configuring options for alternative communications channels based upon the online presence state. For example, when the selected contact is online, the communications channels may include e-mail and IM.

The online menu options may be pre-stored at the host system 110, the client system 105, or other remote data store. Alternatively, the online menu options may be generated on-the-fly by the host system 110 or the client system 105 based upon a set of rules. FIG. 7 describes an exemplary interface available to a user when the selected contact is online. FIGS. 8-10 describe exemplary interfaces available to a user when the selected contact is online, where additional online presence information is available. In particular, FIG. 8 describes an exemplary interface that may be presented when the selected contact is using a mobile device, FIG. 9 describes an exemplary interface that may be presented when the selected contact is idle, and FIG. 10 describes an exemplary interface that may be presented when the selected contact is unavailable. Other interfaces may be presented based upon other online presence information.

If the selected contact is offline, the offline menu options are determined for the selected contact (step 455) and the menu is rendered with the offline options (step 460). The offline menu options are options which are desired to be presented to the user when the desired contact is offline or otherwise unavailable. Determining the offline menu options may include configuring options for alternative communications channels based upon the online presence state. For example, when the selected contact is offline, the communications channels may include e-mail but not IM.

The offline menu options may be pre-stored at the host system 110, the client system 105, or other remote data store. Alternatively, the offline menu options may be generated on-the-fly by the host system 110 or the client system 105 based upon a set of rules. FIG. 11 describes an exemplary interface available to a user when the selected contact is offline. Also, if it is not possible to determine the online presence status of the selected contact, the user may be prompted to take appropriate action. For example, if the contact lacks an instant messaging screen name, the user may be prompted to enter a screen name.

The order of steps 405-470 may vary. For example, the client system may connect to the host (step 410) before the address book UI is loaded or invoked (step 405), and the contact may be selected (step 430) before the online presence information is received (step 425). Certain steps may be combined or omitted entirely, as appropriate. Referring to FIG. 4B, a client system 105 and a host system 110 interact according to a procedure 400B to transmit electronic data. Initially, a sender (e.g., a contact) transmits electronic data to the host system 110 (step 475). In one implementation, the sender is a client system 105 associated with a contact who is an end user of the communication system 100. In another implementation, the sender aids the client system in transmitting electronic data through a communications link 115 to the host system 110. In yet another implementation, the sender is a server, such as a processing server, within the host system 110. For example, the processing server may be a web mail server arranged to store and forward electronic data transmitted between end users of the communication system 100.

The host system 110 receives the electronic data from the sender (step 477). In one implementation, the mail gateway receives the electronic data from the client system 105 and/or the processing server. Typically, the mail gateway will receive electronic content from subscribers through a dial up telephone network or DSL (digital subscriber line) and will receive electronic content from non-subscribers indirectly through the Internet. The mail gateway may perform protocol conversions if necessary to receive electronic content from non-subscribers.

After receiving the electronic data from the client system 105 (step 477), the host system 110 determines one or more attributes of the electronic data (step 479). Attributes of the electronic data may include, but are not limited to, an identification token, the author of the electronic data, the recipient(s) of the electronic data, the subject of the electronic data, the date and time of the transmission, and/or whether the electronic data contains attachments or embedded images. The host system 110 typically will store the contents and attributes of the electronic data. For example, in one implementation, contents of the electronic data are stored in a storage area on the host system 110 and the attributes of the electronic data are cached locally in a server on the host system 110 and also stored in a database on the host system 110, such as, for example, a tandem database. The body of the electronic data is stored in databases on the host system 110 such as, for example, electronic content databases. Attachments are stored in a different database on the host system 110, such as, for example, an attachment database. In this example, the body of the electronic data is stored twice to assure its availability. Due to the typically large sizes of attachments, however, such objects are only stored once to conserve memory space.

The tandem database 110 includes a system of folders corresponding to the subscribers of the host system 110. Each folder may have properties assigned by the subscriber including, for example, properties for filtering electronic content from certain sources. When electronic data are received, the folder stores the attributes of the electronic data including the location(s) of the electronic data content (i.e., body and attachments) in the storage area on the host system 110.

The host system 110 then configures an alternate communications channel between the intended recipient and the client system 105 and/or configures an alternate communications channel between the intended recipient and other recipients based on the detected attributes of the electronic data (step 481). As described with respect to FIG. 4A, menu options may be determined and a menu may be rendered based upon the attributes of the electronic data and/or the availability of alternate communication channels.

FIG. 4C illustrates one implementation of a procedure 400C for configuring menu options that enable an alternate communications channel. Initially, the host system 110 detects an identification token associated with incoming electronic data (e.g., an e-mail message) (step 485). The identification token may be intercepted by the host system 110 and/or presented to the host system 110 by the client system 105. By referencing the token, the host system 110 accesses a cache (step 487) and determines whether attributes of the electronic data are stored locally (step 489). Such attributes may include, but are not limited to, a listing of the sender and all recipients associated with the electronic data.

If attributes of the electronic data are stored locally, the host system 110 retrieves the attributes from the local cache (step 491). If, on the other hand, attributes of the electronic data are not stored locally, the host system 110 determines the attributes of the electronic data (step 493) and then stores the attributes in a local cache (step 495). The host system 110 may determine the attributes of the electronic data itself and/or may access another server to determine the attributes. In one implementation, the attributes of the electronic data include a listing of the sender and the recipients associated with the electronic data.

In one implementation, the host system 110 listing includes e-mail addresses of subscribers and non-subscribers of the communications system 100. The host system 110 strips the domain (e.g., @aol.com) from the e-mail address of a subscriber (contact) with a recognized domain to obtain the subscriber's IM screen name (step 497). This step facilitates the reverse look-up process.

The host system 110 determines the instant messaging capability of each of the e-mail addresses and/or screen names (step 499). For example, the host system may check to see whether a screen name is associated with an active account having IM capability and, if so, obtain the online presence state of the screen name.

In one implementation, the host system 110 provides a menu option to send an invitation to those contacts without instant messaging capability to become IM capable. For those contacts with instant messaging capability, the host system 110 identifies the online presence state of the particular contact (e.g., online, offline, away, busy, or not IM capable). The online presence of a particular contact can be detected, for example, from a persistent connection to an IM server and/or the activity of a specific control port. As discussed, a particular graphical user interface is displayed to the user based on the IM presence state of the contact. For example, upon opening an e-mail message from a contact, the user may receive one or more redirection commands based on the IM state of the contact and/or any other addressees of the e-mail message. The redirection command may include a URL for navigating the user's browser to a particular URL associated with a graphical user interface and/or icon corresponding to one of the IM states.

In an HTML-based environment, the redirection command may include source code such as, for example:

<AHREF=“emailaction.tmpl?from=user@domain.com&email=user@domain.com&name=&givenname=&sn=”><IMGSRC=“http://imserver.imhostcomplex.osp.com:80/user@domain.com?on_url=http://tristate.team.com/webmail/br/nc/images/online.gif&off_url=http://tristate.team.com/webmail/benc/images/offline.gif&noexist_url=http://tristate.team.com/webmail/benc/images/noexists.gif” WIDTH=16 HEIGHT=16 BORDER=0></A> <AHREF=“emailaction.tmpl?from=user@domain.com&email=user@domain.com&name=&givenname=&sn=”>user@domain.com</A>

When the source code is rendered by a browser application, a state image may be shown even if the contact is off-line or not IM capable. Each state typically is associated with a different image. In this example, a fixed height and width attribute is placed in the [Unable to display image] tag, which allows the web page to render before the images have been resolved.

FIG. 5 illustrates an example of an address book UI 500 that may be presented to a user. The UI 500 includes a contact list 505 populated with one or more contacts 510. The contacts 510 may be one of several types, including an individual contact and a group contact. A group contact typically is a collection of one or more individual contacts. Each contact may include a name of the contact and one or more icons 515 associated with the contact. The icons 515 may indicate, for example, the online presence state of the contact. The icons 515 may also indicate a property of the contact, such as, for example, whether the contact is an individual or a group contact. As shown, contacts 510 a, 510 b, 510 c, 510 d, 510 e, 510 f, 510 g, 510 h, 510 i, 510 j, 510 k, 510 l, and 510 m are displayed and associated with icons 515 a, 515 b, 515 c, 515 d, 5151 e, 515 f, 515 g, 515 h, 515 i, 515 j, 515 k, 515 l, and 515 m. In general, the UI 500 is rendered on the client system 105 using software stored on the client system 105.

The UI 500 also includes controls 520 and controls 530 for taking an action with respect to a contact or contacts 510. As shown, controls 520 include a control 522 to send an e-mail message to a selected contact, a control 524 to copy an e-mail message to a contact, and a control 526 to send a blind copy of an e-mail to a contact. Controls 530 include a control 532 to add a contact to the address book, a control 534 to add a group contact (group) to the address book, a control 536 to edit information about a contact in the address book, a control 537 to delete a contact, and a control 538 to print information about a contact. Other controls, such as a control to send an instant message to a contact, may be provided in UI 500. The controls, including controls 520 and 530, may be intelligently enabled depending upon the online status of the contact in the address book.

In addition, the UI 500 may include a search window 540 and a contact details window 545. The search window 540 enables a user to locate a contact by searching for one or more contact attributes in the address book. In one implementation, the user may search for contacts who have a specified online presence state. For example, the user may search for contacts who are online. The contact details window 545 is used to display detailed information about a selected contact.

FIG. 6 illustrates an example of an address book UI 600 that may be presented to a user who has selected a contact. As shown, the contact 510 k has been selected from among the contacts in the contact list 505. The user may manually select the contact 510 k using an input device, or the contact 510 k may be automatically selected by a computer program, such as a computer program running on the client system 105.

Contact details window 545 provides additional information related to the selected contact 510 k. The information includes one or more of the following: the contact name 605; a title 610; a company 615; a screen name 620, which may further include a link 625 to a communication program for communicating with the screen name and an online presence status 630; e-mail addresses 635 and 640; and a home address 645, including a city 650, state (not shown), ZIP code (not shown), and a country (not shown). The information may also include one or more of the following (not shown): a work address, including a city, state, ZIP code, and country; telephone numbers, including telephone numbers for home, work, fax, cellular, and pager; a home page on the Internet; a birthday; an anniversary; a spouse's name; family member names and relationships; notes; and a category. The online presence status 630 may include an icon or a description representative of the online presence status. The online presence status 630 may be updated by information from the host system 110 or the client system 105. An icon 515 k may also be displayed, and may represent the online presence status 630.

FIG. 7 illustrates one example of a UI 700 that may be presented to a user of an address book program. The UI 700 may be invoked manually through user manipulation of an input device, or may be invoked automatically, for example, upon the occurrence of some event such as the receipt of a communication from a contact. The UI displays an online presence state 705 for the screen name 625, and the menu choices 710 are enabled based upon the online presence state 705. As shown in FIG. 7, the contact has a presence state 705 of online.

The UI 700 contains intelligently enabled menu choices for actions that may be taken with respect to a contact 510 in the address book based upon the online presence state of the contact 510. The menu choices 710 may be pre-stored, or may be configured on-the-fly based upon the online presence state 705. Also, during transition from one online presence state to a different state, a smoothing technique may be implemented to avoid excessive re-configuration of menu options. Intelligently enabling the menu choices 710 includes adding, changing, deleting, enabling, or graying out or otherwise disabling the menu choices. Typically, the menu choices enabled are those that are appropriate in the context of the current online presence state. For example, if the contact is offline, a menu option to send an instant message 720 will be removed or disabled.

In the example of FIG. 7, the UI 700 includes menu choices 710 for a contact 510 k having a screen name 625. The menu choices 710 include options to send e-mail 715, send an instant message 720, add the contact to a buddy list 725, block e-mail from the contact 730, view the contact's profile information 735, view a web page associated with the contact 740, block instant messages from the contact 745, share music 750, share video 755, and start a webcam 760.

FIG. 8 illustrates another example of a UI 800 that is similar to UI 700 and may be presented to a user of an address book program. The UI 800 contains intelligently enabled menu choices for actions that may be taken with respect to a contact 510 in the address book based upon the online presence state of the contact 510.

The UI 800 displays an online presence state 805 for the screen name 625, and the menu choices 810 are enabled based upon the online presence state 805, which in this case indicates that the contact is using a mobile device. Menu choices are enabled as appropriate in the context of the current online presence state. For example, since the contact is using a mobile device, a menu option to initiate a phone call 815 may be added. As shown, the UI 800 includes menu choices 810 to send e-mail 715, send an instant message 720, add the contact to a buddy list 725, block e-mail from the contact 730, view the contact's profile information 735, view a web page associated with the contact 740, and initiate a telephone call with the contact 815 at the contact's mobile device phone number. The option to block instant messages 745, discussed with respect to FIG. 7, has been removed from the menu choices 810.

FIG. 9 illustrates another example of a UI 900 that is similar to UIs 700 and 800 and may be presented to a user of an address book program. The UI 900 contains intelligently enabled menu choices for actions that may be taken with respect to a contact 510 in the address book based upon the online presence state of the contact 510.

The UI 900 displays an online presence state 905 for the screen name 625, and the menu choices 910 are enabled based upon the online presence state 905, which in this case indicates that the contact is idle. Menu choices are enabled as appropriate in the context of the current online presence state. For example, since the contact is idle, a menu option to block instant messages from the contact 745 may be removed. As shown, the UI 900 includes menu choices 910 to send e-mail 715, send an instant message 720, add the contact to a buddy list 725, block e-mail from the contact 730, view the contact's profile information 735, and view a web page associated with the contact 740. Since the contact is not using a mobile device, the menu choice to initiate a telephone call with the contact 815, discussed with respect to FIG. 8, is not presented here. However, in other implementations, the option to initiate a telephone call could be presented whenever a telephone number (land line and/or mobile) is available for the contact.

FIG. 10 illustrates another example of a UI 1000 that is similar to UIs 700, 800, and 900 and may be presented to a user of an address book program. The UI 1000 contains intelligently enabled menu choices for actions that may be taken with respect to a contact 510 in the address book based upon the online presence state of the contact 510.

The UI 1000 displays an online presence state 1005 for the screen name 625, and the menu choices 1010 are enabled based upon the online presence state 1005, which in this case indicates that the contact is away. Menu choices are enabled as appropriate in the context of the current online presence state. For example, since the contact is away, menu options to send an instant message 720 and to block instant messages from the contact 745 may be removed. As shown, the UI 1000 includes menu choices 1010 to send e-mail 715, add the contact to a buddy list 725, block e-mail from the contact 730, view the contact's profile information 735, and view a web page associated with the contact 740.

FIG. 11 illustrates another example of a UI 1100 that is similar to UIs 700, 800, 900 and 1000 and may be presented to a user of an address book program. The UI 1100 contains intelligently enabled menu choices for actions that may be taken with respect to a contact 510 in the address book based upon the online presence state of the contact 510.

The UI 1100 displays an online presence state 1105 for the screen name 625, and the menu choices 1110 are enabled based upon the online presence state 1105, which in this case indicates that the contact is offline. Menu choices are enabled as appropriate in the context of the current online presence state. For example, since the contact is offline, menu options to send an instant message 720 and to block instant messages from the contact 745 may be removed. Also, menu choices to view the contact's profile information 735 and view a web page associated with the contact 740 have been removed. As shown, the UI 1100 includes menu choices 1110 to send e-mail 715, add the contact to a buddy list 725, and block e-mail from the contact 730.

FIG. 12 illustrates another example of a UI 1200 that is similar to UIs 700, 800, 900, 1000, and 1100 and may be presented to a user of an address book program. The UI 1200 contains intelligently enabled menu choices for actions that may be taken with respect to a contact 510 in the address book based upon a determination that the contact 510 does not have the capability to communicate by IM or does not have an associated IM screen name.

The UI 1200 displays an online presence state 1205 for the screen name 625, and the menu choices 1210 are enabled based upon the online presence state 1205, which in this case indicates that the contact is not IM capable. Menu choices are enabled as appropriate in the context of the current online presence state. For example, since the contact is not IM capable, menu options to send an instant message 720, add the contact to a buddy list 725, and to block instant messages from the contact 745 may be removed. Also, menu choices to view the contact's profile information 735 and view a web page associated with the contact 740 have been removed. As shown, the UI 1200 includes menu choices 1210 to send e-mail 715, block e-mail from the contact 730, and invite the contact to join an IM service 1215 so as to become IM capable.

Other implementations are within the scope of the following claims. For example, other online presence states may be defined and used to intelligently enable menu choices. In addition, menu choices in an address book may be intelligently enabled based upon other factors. For example, if a contact has already been added to an instant messaging buddy list of the user, the option to add the contact to the buddy list may be disabled. In another example, if the contact does not have a phone number stored, an option to call the contact may not be presented. In yet another example, the menu choices may be intelligently enabled based upon the e-mail address of the sender. For instance, additional menu choices may be enabled for a contact having a given hostname and/or domain name in their e-mail address, such as “aol.com,” which may be associated with an “aol.com” screen name. Also, the user interface may be a viewable interface, an audible interface, a tactile interface, or any combination of these. 

1. A computer implemented method for intelligently enabling menu choices, the method comprising: rendering, on a client system, an address book user interface comprising information related to one or more contacts; selecting a contact from the address book user interface; determining an online presence for the selected contact; enabling one or more menu options based upon the determined online presence state, with menu options enabled for a first online presence differing from menu options enabled for a second online presence state; and presenting the enable menu options to a user in a a user interface. 2-46. (canceled) 